Skip to content

Add LPM latency measurements and refactor LPM power tables#399

Merged
praneethbajjuri merged 2 commits into
TexasInstruments:masterfrom
kwillis01:latency-measurements
Jul 21, 2025
Merged

Add LPM latency measurements and refactor LPM power tables#399
praneethbajjuri merged 2 commits into
TexasInstruments:masterfrom
kwillis01:latency-measurements

Conversation

@kwillis01

Copy link
Copy Markdown
Contributor

feat(linux): AM62*: Introduce LPM resume latency performance

Add the LPM resume latency performance for AM62 family of devices.

Signed-off-by: Kendall Willis <k-willis@ti.com>

refactor(linux): AM62*: Add LPM subheading and name tables

Add a subheading for the power performance of LPM. Add the table names
to the csv-table instead of being text before the table.

Signed-off-by: Kendall Willis <k-willis@ti.com>

Add a subheading for the power performance of LPM. Add the table names
to the csv-table instead of being text before the table.

Signed-off-by: Kendall Willis <k-willis@ti.com>
@kwillis01

Copy link
Copy Markdown
Contributor Author

To address the vale comments:
IMO sentence case should not be used for headings, and capitalizing every word seems better, let me know if sentence case is chosen to go forward for headings, and I will change it.
Also, the instance of passive voice makes the most sense to me because the latency measurements are measured that way. If I were change to active voice I think it would have to be something like this: "To measure the latency performance, suspend the Linux printk logs." This doesn't make sense in this context because I am saying how the latency is measured not telling people to do it in some way. Let me know if I am thinking of it incorrectly, or if there is a different way to use active voice

Add the LPM resume latency performance for AM62 family of devices.

Signed-off-by: Kendall Willis <k-willis@ti.com>
@kwillis01 kwillis01 force-pushed the latency-measurements branch from 54d2021 to 74a3fdf Compare July 18, 2025 22:09
@praneethbajjuri

Copy link
Copy Markdown
Collaborator

Are these perf report refactoring changes coming from test-reports repo with automated execution? If not, preferably fixing there is needed instead of tweaking the generated output.

@kwillis01

Copy link
Copy Markdown
Contributor Author

Are these perf report refactoring changes coming from test-reports repo with automated execution? If not, preferably fixing there is needed instead of tweaking the generated output.

@praneethbajjuri LPM doesn't have any perf results coming from test-reports repo yet. This is something we will have to work on for the future.

@StaticRocket StaticRocket left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Heads up, that refactor should be made upstream in test-reports as well

@praneethbajjuri praneethbajjuri merged commit 8325481 into TexasInstruments:master Jul 21, 2025
5 of 6 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants